<HTML>
<HEAD>
<meta charset="UTF-8">
<title>BankAccount.status - stripe</title>
<link rel="stylesheet" href="../../../style.css">
</HEAD>
<BODY>
<a href="../../index.html">stripe</a>&nbsp;/&nbsp;<a href="../index.html">com.stripe.android.model</a>&nbsp;/&nbsp;<a href="index.html">BankAccount</a>&nbsp;/&nbsp;<a href="./status.html">status</a><br/>
<br/>
<h1>status</h1>
<a name="com.stripe.android.model.BankAccount$status"></a>
<code><span class="keyword">val </span><span class="identifier">status</span><span class="symbol">: </span><span class="identifier">Status</span><span class="symbol">?</span></code>
<p>For bank accounts, possible values are <code>new</code>, <code>validated</code>, <code>verified</code>, <code>verification_failed</code>,
or <code>errored</code>. A bank account that hasn’t had any activity or validation performed is new.
If Stripe can determine that the bank account exists, its status will be <code>validated</code>. Note
that there often isn’t enough information to know (e.g., for smaller credit unions), and
the validation is not always run. If customer bank account verification has succeeded,
the bank account status will be <code>verified</code>. If the verification failed for any reason,
such as microdeposit failure, the status will be <code>verification_failed</code>. If a transfer sent
to this bank account fails, we’ll set the status to <code>errored</code> and will not continue to send
transfers until the bank details are updated.</p>
<p>For external accounts, possible values are <code>new</code> and <code>errored</code>. Validations aren’t run
against external accounts because they’re only used for payouts. This means the other
statuses don’t apply. If a transfer fails, the status is set to <code>errored</code> and transfers
are stopped until account details are updated.</p>
<p><a href="https://stripe.com/docs/api/customer_bank_accounts/object#customer_bank_account_object-status">status</a></p>
</BODY>
</HTML>
